Skip to content

Conversation

@relud
Copy link
Contributor

@relud relud commented Nov 3, 2025

experimenter is switching to server-side glean in mozilla/experimenter#13859

@badboy
Copy link
Member

badboy commented Nov 4, 2025

The dry-run looks good:

python3 -m probe_scraper.runner --dry-run --cache-dir tmp/cache --out-dir tmp/out --glean --glean-limit-date 2025-11-02 --output-bucket=gs://probe-scraper-prod-artifacts/ --glean-url https://github.com/mozilla/experimenter --glean-url https://github.com/mozilla/glean_parser

afau this should all work just fine: glean-server is not a full glean, but it does have the events ping, so that table will be re-used. the other existing tables won't be used.
I will verify that this "won't be used" is fine or if that results in automatic deletion or something.

@akkomar
Copy link
Contributor

akkomar commented Nov 4, 2025

(...) I will verify that this "won't be used" is fine or if that results in automatic deletion or something.

This will trigger deletions. Glean-server declares only events ping (https://github.com/mozilla/glean_parser/blob/main/server_telemetry/server-side-pings.yaml), so other pings currently inherited from glean-core (https://dictionary.telemetry.mozilla.org/apps/experimenter_backend?itemType=pings&page=1) - baseline, deletion-request, health, metrics - will disappear in schema generation. This will cause schema generator to fail and production schema deploys to stop.

If these pings were not used and removal of their tables is desired (@relud?)we can add them to https://github.com/mozilla/mozilla-schema-generator/blob/main/incompatibility-allowlist to allow that.

@relud
Copy link
Contributor Author

relud commented Nov 4, 2025

yeah those tables should be deleted

@relud
Copy link
Contributor Author

relud commented Nov 4, 2025

filed mozilla/mozilla-schema-generator#299 to allow the deletes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants